Best practices for OvrC Locations

Follow these steps when creating and planning OvrC Locations to get the most out of the platform:

  1. Set up OvrC as you begin the project. Doing so helps with organization and can be updated throughout the installation, to have the most complete information possible. Setting up an OvrC location after the installation often leads to incomplete or inaccurate information and duplicated efforts in some cases.

  2. Create naming standards within your company. These should be used for customer name, job code, device names, etc. This creates consistency in your OvrC account and keeps everything clear and organized.

  3. Use the Job Code field to identify customers. Use job codes to track customers on a service plan, under warranty, or in progress. Job codes help you filter your customer list and notifications with just a few keystrokes. Examples include: In progress, Connect, Assist, or Surveillance.

  4. Verify the location with the customer. As you enter an address, OvrC cross-checks it with Google Maps, providing potential verified addresses close to your location. Once you see the correct address, click it and OvrC will fill in the remaining details of the address.

    In the rare case where the development is so new that Google Maps does not know about it yet, you can use a Plus Code to capture the location using coordinates.

  5. Create Rooms for the location. Rooms make troubleshooting and configuration easier by grouping devices under a physical location to help you focus on a specific area of the project. Read more about Rooms here.

  6. Claim your devices. The best practice is to claim an OvrC Pro device fist so it will scan the location for the rest of the connected devices, instead of having to manually enter the MAC address and Service Tag of each device.

  7. Register controllers for Control4 projects. If this is a Control4 location, go to the Categories tab to Start a New Project and register the controller.

    Pro Tip: -_The Rooms features has a one-way sync from OvrC to Composer. Create all the project rooms in OvrC to avoid duplicate rooms in Composer.

    Note: -__.Only one primary controller can be registered to a single location.

  8. Hand off the project to the customer. Give the customer access to their system’s applications. Whether that’s OvrC Connect, Control4 Connect, Assist, Assist Premium, or Luma Insights.